0.1.0 (2024-03-31).md
Unicode text, UTF-8 text
Changelog for version 0.1.0
This is the first non-patch update to the project, still in άλφα state.
New features in this release
Give each user a
.config
repo, which is used for storing settings, like userstyles.Userstyles can be added to the
.config
repo under the nametheme.css
, and they will be applied to the UI.Efficient UI CSS variables can be overridden as well.
The
.config
repo is created automatically when a user is created.The
.config
repo is private by default, but can be made public or unlisted like any other.Right now, the
.config
repo is not used for anything else, but it will be in the future.When repo deletion will be added, the
.config
will not be deletable.Currently, it is not possible for previous users to get a
.config
repo, but this will be added very soon.
Render markdown files, like this one, on file pages.
Markdown comments are not yet rendered: that requires caching so loading comments is not too slow.
Markdown is rendered using a custom renderer, which isnot CommonMark compliant.
Some features are missing, but it supports extra features like diffs or
strikethrough, and even 7-star emphasis. Missing features include: Tables Footnotes Definition lists Task lists Indented code blocks Ordered lists (will be fixed with patch) ID attributes Subscript and superscript Setext headers URL title attributes Backslash escaping for format specifiers * HTML entitiesOld features like trailing space hard breaks are not supported.
No subset of HTML is rendered yet.
Changed features in this release
Make the tab component styling look nicer.
Colour now matches the nav tabs.
Fixed bugs in this release
The
safari-pinned-tab.svg
file now matches the updated logo.Before it matched a really similar development logo.
When accessing a nonexistent repository from the web interface, it now returns a 404 error instead of a 403 error.
This was because the access control was done before the repository existence check.
1Changelog for version 0.1.0 2=========================== 3 4This is the first non-patch update to the project, still in άλφα state. 5 6New features in this release 7---------------------------- 8 9* Give each user a `.config` repo, which is used for storing settings, like 10userstyles. 11* Userstyles can be added to the `.config` repo under the name `theme.css`, 12and they will be applied to the UI. 13* Efficient UI CSS variables can be overridden as well. 14* The `.config` repo is created automatically when a user is created. 15* The `.config` repo is private by default, but can be made public or 16unlisted like any other. 17* Right now, the `.config` repo is not used for anything else, but it will 18be in the future. 19* When repo deletion will be added, the `.config` will not be deletable. 20* Currently, it is not possible for previous users to get a `.config` repo, 21but this will be added very soon. 22* Render markdown files, like this one, on file pages. 23* Markdown comments are not yet rendered: that requires caching so loading 24comments is not too slow. 25* Markdown is rendered using a custom renderer, which is _not_ CommonMark 26compliant. 27* Some features are missing, but it supports extra features like ++diffs++ or 28~~strikethrough~~, and even *******7-star emphasis*******. 29* Missing features include: 30* Tables 31* Footnotes 32* Definition lists 33* Task lists 34* Indented code blocks 35* Ordered lists (will be fixed with patch) 36* ID attributes 37* Subscript and superscript 38* Setext headers 39* URL title attributes 40* Backslash escaping for format specifiers 41* HTML entities 42* Old features like trailing space hard breaks are not supported. 43* No subset of HTML is rendered yet. 44 45Changed features in this release 46-------------------------------- 47 48* Make the tab component styling look nicer. 49* Colour now matches the nav tabs. 50 51Fixed bugs in this release 52-------------------------- 53 54* The `safari-pinned-tab.svg` file now matches the updated logo. 55* Before it matched a really similar development logo. 56* When accessing a nonexistent repository from the web interface, it now returns 57a 404 error instead of a 403 error. 58* This was because the access control was done before the repository existence 59check.